Property transaction

ABSTRACT

Methods, devices, and systems are provided for property transactions. One device embodiment includes a processor, a memory coupled to the processor, and user interface coupled to the memory and processor. The device includes program instructions storable in memory and executable by the processor to associate real property map grid data, having page and section identifiers with property data for the real properly; record an assignment of a section associated with the map grid data to a listing agent; and record at least one indicator, having a number of levels representing a party&#39;s interest in a transaction involving real property in the section.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.10/893,458, filed Jul. 16, 2004, the specification of which isincorporated herein by reference.

INTRODUCTION

The traditional method of selling real or personal property begins witha seller coming to the conclusion that she/he is ready, willing and ableto sell the property in question. Upon deciding to sell, the sellerbegins to market their property, by word of mouth, posting a for salesign on the property, buying newspaper ads, marketing their property ona web site or in the ease of real property, listing their property on aMultiple listing Service, etc., thus commencing “market time”. Theinherent flaw with this system of marketing is that it begins at thepoint the seller has indicated they are ready, willing and able to sell.The property owner has lost the opportunity to market their propertyovertime while capturing the level of buyer interest in the property asit changes. Likewise, the property owner currently does not have accessto an efficient and unobtrusive method of monitoring the level ofinterest in their property before they are actually ready, willing orable to sell. Moreover, the sale of real or personal property may justbe a question of terms and conditions. In which case, the current methodof market exposure fails miserably.

For example, consider the case of a relocation buyer who is particularlyattracted to the homes in a specific neighborhood or is enamored withlocal amenities etc. The choices of real property in the current marketare limited to houses on a Multiple Listing Service or homes with a ForSale By Owner sign in the front yard. There is currently no way to inputa buyer need into a system and notify home owners that someone isinterested in moving into their neighborhood. Also, in the case of real,property, the event that solicits the home owner's or buyer's ready,willing, and able status may be a “stay in touch” phone call, directmail, door-to-door solicitation or attendance of an open house. All ofwhich are blind events in which a real estate professional is hoping forpositive results. There is no event driven bi-directional notificationand communication conduit over time that collects buyers and sellers toeach other and to real estate professionals and lenders. Likewise, apersonal property owner, let's say of farm equipment has no way tocatalog his/her equipment and market it in advance of being readywilling and able to sell, thus possibly missing out on a ready, willingand able buyer who would be willing to pay top dollar, thus allowing theseller to upgrade his or her equipment.

Real estate agents working in the current system are incrediblyinefficient. One agent, may market their services or listings viaadvertising in publications, bus benches, costly direct mail, openhouses where one may sit for hours hoping a prospective client will walkthrough the door. While completely different agents will be driving allover a particular region hoping they can find a house that is for sale,that meets their client's needs and that is not pending a closing orsold. Either way, whether an agent is looking for properties to list orbuyers to represent, it is a guessing game. There is so current systemthat allows customers to indicate their readiness, willingness andability to buy or sell.

If buyers and sellers had such a system they would be able to merelychange a single Ready, Willing, and Able (RWA) indicator which wouldtrigger system events notifying agents, buyers and sellers of their newrating. Other agents, buyers and sellers would then have the opportunityto respond to the event notifications they receive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a system embodiment according to theteachings of the present invention.

FIG. 2 is another illustration of a system embodiment according to theteachings of the present invention.

FIGS. 3A and 3B are table diagrams representing a non-exhaustive list ofa number of truth tables, represented in this example as ready, willing,and able truth tables for a buyer and a seller of property, which catsbe associated with the indicator level embodiments described herein.

FIG. 4 is a time line embodiment associated with property transactionembodiments of the present invention including the ready, willing, andable truth tables shown in FIG. 3.

FIG. 5 illustrates an embodiment for a public interface.

FIG. 6 is a block diagram representing a login embodiment.

FIG. 7 is a block diagram representing in more detail an embodiment forthe “my account prospect” block shown in FIG. 6.

FIG. 8 is a block diagram representing in more detail an embodiment forthe “seller profile” block shown in FIG. 7.

FIG. 9 is a block diagram representing in more detail an embodiment forthe “buyer profile” block shown in FIG. 7.

FIG. 10 is a block, diagram representing in more detail an embodimentfor the “preferences” block shown in FIG. 7.

FIG. 11 is a block diagram representing in more detail an embodiment forthe “browse” block shown in FIG. 7.

FIG. 12 is a block diagram representing in more detail an embodiment forthe “search” block shown in FIG. 7.

FIG. 13 is a block diagram representing in more detail an embodiment forthe “watchlist” block shown in FIG. 7.

FIG. 14 is a block diagram representing in more detail an embodiment torthe “buyer/seller toolbar” block shown in FIG. 7.

FIG. 15 is a block diagram representing in more detail an embodiment forthe “my account agent” block shown in FIG. 6.

FIG. 16 is a block diagram representing in more detail an embodiment forthe “home owner prospector” block shown in FIG. 15.

FIG. 17 is a block diagram representing in more detail art embodimentfor the “customer relationship management” block shown in FIG. 15.

FIG. 18 is a block diagram representing in more detail m embodiment forthe “buyer/seller prospect hotlist” block shown in FIG. 17.

FIG. 19 is a block diagram representing in more detail an embodiment forthe “zoom in prospect status” block shown in FIG. 18.

FIG. 20 is a block diagram representing in more detail an embodiment forthe “agent toolbar” block shown in FIG. 15.

FIG. 21 is a block diagram representing in more detail an embodiment forthe “home owner prospect capture” block shown in FIG. 15.

FIG. 22 is a block diagram, representing in more detail an embodimentfor the “map page section auction” block shown in FIG. 15.

FIG. 23 is a block diagram representing in more detail an embodiment,for the “my farm” block shown in FIG. 15 illustrating detail for mapsection value and market share.

FIG. 24 is a block diagram representing in more detail an embodiment forthe “my farm” block, shown in FIG. 15 illustrating detail for marketshare analysis per map page section.

FIG. 25 is a block diagram representing an embodiment for an indicatorassociated with a seller of property, represented in this example as anumber of ready, willing, and able indicator levels.

FIG. 26 is a block diagram representing an embodiment tor an indicatorassociated with a buyer of property, represented in this example as anumber of ready, willing, and able indicator levels.

FIG. 27 is an illustration of a method embodiment.

FIG. 28 is an illustration of another method embodiment.

DETAILED DESCRIPTION

Embodiments of the present invention include methods, systems, anddevices for property transactions. For example, in accordance withvarious embodiments of the present invention, there are providedprospective buyers and prospective sellers. The prospective buyers canenter their buyer needs into a computerized system along with anindicator having a number of levels representing, e.g., indicating, thebuyer's readiness, willingness and ability to buy whatever they areinterested in buying at that particular moment in time. In variousembodiments this indicator is referred to as a Ready, Willing and Able(RWA) indicator. Likewise, prospective sellers can enter their sellerneeds into a computerized system along with their RWA indicator,indicating their readiness, willingness and ability to sell whateverthey are interested in selling at that particular moment in time. Hereina reference to a “seller” may be to the seller, the seller's property orthe combination thereof. In the various embodiments, these indicatorshaving a number of levels, e.g., a RWA scale, are expressed as a rangeof numbers. By way of example and not by way of limitation, a RWA scalewhich ranges from 1-5 is used in various embodiments of the presentdisclosure.

For example, in one embodiment Buyer RWA self ratings are defined asfollows:

-   1: Will not buy-   2: Neutral-   3: May buy-   4: Will buy for the right property with the right terms and    conditions-   5: Will inspect, tour or preview property (In the ease of real    property, buyer is pre-approved to buy property up to a certain    dollar amount).

And, in one embodiment Seller RWA self ratings are defined as follows:

-   1: Will not sell-   2: Neutral-   3: May sell-   4: Will sell for the right terms and conditions (In the case of real    property if selling principle residence, identity has been    verified).-   5: Will allow and schedule, inspections, tours, previews etc. and    will consider all offers from buyers with a “5” Ready, Willing and    Able status.

One of ordinary skill in the art will appreciate upon reading thisdisclosure that the embodiments are not limited to the above example.And, as one of ordinary skill in the art will understand reading thisdisclosure, the embodiments described herein provide the ability tomatch motivated, ready willing and able buyers and sellers (e.g., asindicated by their RWA rating) whose needs match and enable them to havea meeting of the minds and engage in a successful business transaction.

According to the various embodiments described herein, there can bethree primary means of matching buyers and sellers. These threeexemplary means of matching buyers and sellers can include: usermanually, albeit electronically, browsing profiles of interest andinteracting with profiles to trigger a system event; user manually,albeit electronically, searching profiles based on certain criteria, andinteracting with profiles to trigger a system event; and, automated,event driven (e.g., unsolicited) and periodic computer generated searchresults or results of general automated/scheduled (e.g., unsolicited)system events. Additionally, in various embodiments, once a buyer orseller has found or received prospective matches the buyer or seller mayadd buyers or sellers to a Watch list, as described in more detailherein. In the event that a watched buyer or seller increases theirassociated indicator rating the watcher, e.g., watching party who placedanother party or entity on the Watch list, will receive eventnotifications, notifying the watcher of activities associated with aparty on the Watch list. For example, a watcher can receive anotification that a watched buyer or seller has changed their associatedindicator rating, e.g., a watched RWA indicator status upgrade. Further,according to various embodiments, the watching party who placed anotherparty or entity on the Watch list can execute instructions to establishthe watcher's notification preferences.

As one of ordinary skill in the art will understand upon reading thisdisclosure, the embodiments can be performed by software/firmware (e.g.,computer executable instructions also referred to as “code”) operable onthe devices shown herein or otherwise. The embodiments of the invention,however, are not limited to any particular operating environment or toexecutable instructions written in a particular programming language.Software/firmware, application modules, and/or computer executableinstructions, suitable for carrying out embodiments of the presentinvention, can be resident in one or several locations.

FIG. 1 is an illustration of a system embodiment, including a number ofdevice embodiments, according to the teachings of the present invention.The system embodiment shown in FIG. 1 includes a networked system 100.Various embodiments of the present invention include a propertytransaction device, for example, the embodiment shown in FIG. 1 includesa server 102 as the property transaction device.

Although the term server is used herein, embodiments of the inventionare not limited to implementation on such a device and variousembodiments can be stand alone devices or systems including a number ofdevices. It is intended that in embodiments using a server, the server102 can be provided by any suitable type of computing device, such aspersonal computers, mainframes, and the like.

Server 102, shown in FIG. 1, includes a processor 105 coupled in amemory 107. Processor 105 and memory 107 can include any type ofprocessor and memory in the art of computing and the various embodimentsarc not limited to where within a device or system a set of computerinstructions reside for use in implementing the various embodiments ofinvention.

Memory can, for example, include Non-Volatile (NV) memory (e.g. Flashmemory), RAM, ROM, magnetic media, and optically read media and includessuch physical formats as memory cards, memory sticks, memory keys, CDs,DVDs, hard disks, and floppy disks, to name a few. Memory can include aDirect Access Storage Device (DASD) or be located on another peripheraldevice that is accessible over a network. One of ordinary skill in theart will appreciate for reading this disclosure that such memory caninclude data stores, application programs (e.g., computer executableinstructions), and the like.

In various embodiments, the server 102 can be connected to a number ofadditional devices 104-1, 104-2, . . . , 104-M, such as remote computingdevices. Alphabetical designator “M” as used herein are intended torepresent any number of additional devices, components, or entitiesbeing discussed. The various designators can represent any value whetheror not the value is the same as a value represented by anotherdesignator. As slated above, the additional devices 104-1, 104-2, . . ., 104-M can be used to allow access to a system or to send informationto the system.

Each remote device 104-1, 104-2, . . . , 104-M can include processor101, memory 102, and display 111 capabilities. The display 111 can beincluded to provide feedback to a user and can include any of varioustypes of computing device displays. The server 102 and/or remote devices104-1, 104-2, . . . , 104-M are capable of including applicationprograms (e.g., computer executable instructions) to cause a server 102or other device 104-1, 104-2, . . . , 104-M to perform particularfunctions as described in more detail below. Examples of remote devicesinclude, but are not limited to, cell phones, lap top computers, desktop computers, workstations, multifunction handheld communicationdevices (e.g., BlackBerryies), intelligent appliances, and the like. Asone of ordinary skill in the art will appreciate upon reading thisdisclosure, the remote devices 104-1, 104-2, . . . , 104-M can includeglobal positioning service (GPS) enabled devices with applicationprograms, e.g., routing and cartographic software/firmware, includedtherein.

As shown in the embodiment of FIG. 1, devices 104-1, 104-2, . . . ,104-M can couple to the server 102 through a first security layer 109-1,or secure data network 109-1. In this way, security can be provided tothe system, however the embodiments of the present invention are notlimited to use of a security layer.

Additionally, devices 104-1, 104-2, . . . , 104-M can couple to theserver 102, such as over various types of networks. For example, thedevices 104-1, 104-2, . . . , 104-M can be coupled to the server 102over a local area network (LAN), e.g., an Ethernet network. The devices104-1, 104-2, . . . , 104-M can also couple to the server 102 over awide area network (WAN), over the public switched telephone network(PSTN), and/or the Internet using transmission control protocol/Internetprotocol (TCP/IP).

Networks, as used herein, can include wireless networks as can beaccessed by desktop devices, laptop devices, mainframe devices, cellphones, multifunction devices (PDAs), and the like. Wireless networkscan include Global System for Mobile communications (GSM) networks,American National Standards Institute (ANSI) networks, Public WirelessLocal Area Networks (PWLANs) including Wi-Fi, among others. Thus,devices described herein can be coupled in either direct hardwiredfashion, e.g. using copper, coaxial cable, optical, fiber connections,and hybrid fiber-coax connection, and/or indirectly in a wirelessfashion using remote electromagnetic signal transmission in the radio ormicrowave frequencies, e.g., RF.

The embodiment shown in FIG. 1 illustrates that the above describedcomponents can couple to additional servers and systems, 106-1, 106-2, .. . , 106-N, over a network as the same has been described above. Suchadditional servers and systems, 106-1, 106-2, . . . , 106-N, can bemaintained by other organizations, or entities. The additional serversand systems, 106-1, 106-2, . . . , 106-N, can include core data storesaccessible by the server 102 according to definable access rights. Theadditional servers and systems, 106-1, 106-2, . . . , 106-N, can includedatabases and executable instructions and/or application programs tooperate on data and can possess processing and routing capabilities overa PSTN or other network as described above.

The additional servers and systems, 106-1, 106-2, . . . , 106-N, caninclude proprietary databases, data modules, and software systemsmaintained by a third party or the like. As shown, the additionalservers and systems, 106-1, 106-2, . . . , 106-N, can be coupled to theserver 102 through a second security layer 109-2, or secure data network109-2 such that data from the additional servers and systems, 106-1,106-2, . . . , 106-N, can be securely exchanged with the server 102,e.g., third party servers connecting to first party servers via TCP/IPutilizing simple object access protocol and XML through a web service.

The server 102, the number of remote devices 104-1, 104-2, . . . ,104-M, and the additional servers and systems, 106-1, 106-2, . . . ,106-N, can all include one or more computer readable mediums havingcomputer executable instructions. As mentioned above, these computerreadable mediums can include devices such as a disk drive for readingdata storage media, e.g. a compact disc, and/or computer readable mediumsuch as random access memory (RAM) and read only memory (ROM),non-volatile, optical, or any other type of memory storage medium.

FIG. 2 is another illustration of a system embodiment according to theteachings of the present invention. The embodiment of FIG. 2,illustrates a property transaction device 220 coupled to a networkinterface 219. The property transaction device 220 can include a server,such as server 102 and/or additional servers 106-1, . . . , 106-N asillustrated in FIG. 1, having processor, memory, and user interfaceresources as described above. Network interface 219 can include a numberof suitable wireless and hardwired network interfaces such as the LANs,WANs, PSTNs, Internet, GSM, ANSIs, and/or PWLANs including Wi-Fi, asdescribed above. As shown in the embodiment of FIG. 2, the propertytransaction device 220 can include application programs 221 and variousdata stores 222 and be coupled to the network interlace 219 through afire wall 223, as the same are known and understood by one of ordinaryskill in the art, for security purposes.

As illustrated and discussed in further detail in connection with FIGS.3-26, the property transaction device 220 includes one or more programmodules associated with application programs 221 and/or data 222.According to various embodiments the application programs 221 andmodules include program instructions storable in the memory andexecutable by the processor to operate on various input information/dataand to output, present, and/or otherwise produce resultant data fromoperation of the instructions la the input information/data. As one ofordinary skill in the art will appreciate upon reading this disclosure,embodiments include various selectably configurable sets of logic.According to various embodiments, and as discussed in more detail below,the application programs 221 and program modules include programinstructions stumble in the memory and executable by the processor tofacilitate property transactions.

In the embodiment of FIG. 2 a third party contributor (TPC) block isillustrated as 213. The TPC 213 can include a remote device or remoteclient, shown as 104-1, 104-2, . . . , 104-M, and/or can include aserver, such as servers 106-1, 106-2, . . . , 106-N, in FIG. 1. As shownin the embodiment of FIG. 2 the TPC 213 can be coupled to the propertytransaction device 220 via a network interface 219 as the same has beendescribed above. The TPC 213 can be used to provide third party content,or data exchange/synchronization, e.g., advertising, customerrelationship management software/system synchronization, and/oraffiliate content, into the various embodiments of the invention.

That is, third party content 213 information can be used to addadditional content to the various embodiments of the present inventionand likewise send data to a third party over the same or similar secureconnection. By way of example and not by way of limitation, and as willbe discussed in further detail below, in various embodiments third partycontent can include regional map data as used by a regional multiplelisting service (MLS). Alternatively and/or additionally, mother exampleof third party content can include data on top listing agents for realproperty in a particular market by volume and/or transaction dollars. Asyet another example, the third party content may include data associatedwith market share analysis relative to real property map datatransaction volume, or dollar. As yet another example, the third partycontent may include tax data information associated with a particularparcel of real property. As yet another example, the third party contentmay include data associated with an auction bidding process hosted by athird party. As yet another example, the third, party content mayinclude any customer or property data from a third party device orsystem, e.g., synchronization with customer relationship managementsoftware. Embodiments, however, are not limited to these examples.Further, by way of example and not by way of limitation, comparativedata can be provided, and used to compare the performance of aparticular individual against performance data available for othersimilarly situated individuals. Information on a particular individualcan be compared with that individual's own assessment information overtime as well as against similarly situated individuals within aparticular region or globally. According to various embodiments theabove third party content can be used m assessing an individual'sperformance, action planning, bidding, etc., as one of ordinary skill inthe art will appreciate upon reading this disclosure. In variousembodiments, the third party content information can be included andanalyzed within the system property transaction device 220 itself and/orthe data collect ion results of various information can be sharedoutside of the system property transaction device 220 with otherentities.

The embodiment shown in FIG. 2 also illustrates that a number ofentities, e.g., buyers 224-1 to 224-P, sellers 225-1 to 225-Q, andagents 226-1 to 226-R can connect to the property transaction device 220through a network interface 219, as the same have been described herein.As one of ordinary skill in the art will appreciate upon reading thisdisclosure, the entities needed within any device or system may bealtered to meet the individual market needs or practices. In variousembodiments, such as the example embodiment of FIG. 2, particular buyers224-1 to 224-P, sellers 225-1 to 225-Q, and agents 226-1 to 226-R canuse remote devices, such as remote devices 104-1, 104-2, . . . 104-Mshown in FIG. 1, to input and retrieve (e.g., exchange) informationwith, the property transaction device 220 through the network, interlace219. As one of ordinary skill in the art will appreciate, in somescenarios, certain entities will only indirectly access or interfacewith the property transaction device 220 on restricted permission basedaccess. As one of ordinary skill in the art will appreciate upon,reading this disclosure, buyers, sellers, and agents access the propertytransaction device 220 at a variety of levels and for a variety ofreasons. As will be explained in more detail below, these variousparties may access the property transaction device 220 for inputting andretrieving information. Likewise, access can be for purposes of updatingand/or modifying information. The embodiments are not limited to theseexamples.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, program embodiments associated with the property transactiondevice 220 can be added in complement from other host sources, e.g.,connected as part of a LAN or WAN, or otherwise, or entirely managedwithin the property transaction device 220 acting as an applicationservice provider (ASP). Thus, in various embodiments programinstructions can be hosted entirely on the property transaction device220, shared with other third party host devices, e.g., additional serversystems 106-1, . . . , 106-N (shown in FIG. 1) coupled over the PSTN,Internet or otherwise, and/or hosted entirely on a separate entity'ssystem and can be managed by the property transaction device 220 througha network interface 219, Embodiments of the invention are not solimited.

The embodiment of FIG. 2 illustrates application programs 221 forreceiving buyer, seller, and/or agent information and which are capableof executing instructions to analyzing such information. Althoughapplication programs 221 can reside an a server such as server 102and/or servers 106-1, . . . , 106-N as described in connection with FIG.1, the embodiments described herein ate not limited to a servercomputing environment. As shown in FIG. 2, the application programs 221can interface with one or many data stores 222, e.g. data servers,enterprise level databases, and the like. Embodiments, however, are notlimited to these examples or to any particular operating and/or networkenvironment (distributed or otherwise) or server configuration. Thedescription included herein is provided for purposes of illustration.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, data stores 222 can have restricted access to allow accessonly to authorized individuals, e.g., authorized administrative users,etc. For example, a server can include a data store that can include anumber of separate partitions to store data and programs for differententities, geographical locations, users, and the like. A server can alsoinclude a data store that can include a number of separate partitions tostore data and programs for each selectably configured set of businessrule according to the program embodiments described herein. As describedin more detail below, the selectably configured business rules caninclude establishing formatting, branding usage, content and contenthandling rules, and the like. Any number of computing devices, such asservers; application programs; and/or data can be distributed as part ofthe property transaction device 220 embodiments described herein.

FIGS. 3A and 3B are table diagrams representing a number of truthtables, represented in this example as ready, willing, and able truthtables for a buyer and a seller of property, which can be associatedwith the indicator level embodiments described herein.

The embodiments shown in FIGS. 3A and 3B highlight some possiblerelationships between a buyer and seller over time and are listed byexample and not limitation. Currently, property owners and serviceproviders market their property, products and services when they areready wiling and able to sell, thus commencing “market time”. Theseller's ultimate objective during the “market time” is to engage in asuccessful business transaction with a buyer who is ready, willing andable to buy.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, a buyer and seller's readiness, and willingness to sell anitem of property can be impacted by their state of mind at any point intime. A buyer and/or seller's state of mind at any point in time can beimpacted by a number of present life circumstances. As used herein, byway example and not by way of limitation, present life circumstances caninclude a new birth, a loss of a family member, a job relocation, aseparation, a promotion, a health condition, financial circumstances,etc.

Further, as used herein by way of example and not by way of limitation,a buyer and seller's “readiness” (R) can include that, individual'spreparedness based on a state of mind resulting from the weighing of thepros and cons regarding buying or selling property or services at aparticular point in time.

The buyer and seller's “willingness” (W) can include a state of mind inwhich the individual wants or desires to conduct a transaction if allterms and conditions are acceptable without undue duress or externalforce or influence.

The buyer and seller's “ableness” (A) can include a state of being ofthe individual's awareness of capability (e.g., menial physical,financial, legal) taking into account external and internal forcesacting upon an individual and the resulting likelihood that anindividual could participate in a transaction even if the individual wascompletely ready and willing. For example, the spouse of the owner mayrefuse to sell an item of property where the sale requires twosignatures to sell or a buyer is ready and willing to buy property butcan not get a required loan pre-approval.

To illustrate an example, a seller may be completely willing to selltheir house for fair market value. He/she may have no barriers standingin his/her way preventing him/her from selling, thus being completelyable. The only problem maybe that a best friend of the seller's child'smay live next door. In this example, the seller will determine the“weight” that the next door friend has m the seller's RWA rating, e.g.,impact on the seller's state of mind primarily affecting the seller's“readiness” factor but for simplicity's sake all RWA indicators areexpressed as an aggregate of the three individual state of mind ratings.

In a given situation, a numerical representation that a buyer and sellerprovide as an indicator level will be a subjective representation of theweights given to any one of the above example factors and lifecircumstances. In various embodiments, certain business rules mayrestrict the numerical representation or change from one numericalrepresentation to another but, outside of such business rules, anindividual's choice of numerical representation will vary fromindividual to individual and from circumstance to circumstance. Forexample, given the exact same circumstances in the example above, twodifferent individuals are likely to “weight” the factors and lifecircumstances differently in choice of numerical representation.

As another example, as one of ordinary skill in the art will appreciateupon reading this disclosure, a buyer may be completely prepared to buya house and completely able to buy a house but is unwilling to agree tolook at a property. Again, the factors, life circumstances and numericalindicator level ratings discussed above are subjective and can bedetermined by the individual given, general, rating guidelines andbusiness rules described in the network system embodiments and propertytransaction device embodiments discussed below.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure and with reference to the indicator level embodiments (e.g.,RWA ratings) described herein, buyers and sellers can leverage time thusextending the traditional concept of market time to “all time”. Thus,rather than waiting until a party is ready willing and able, e.g.,expressed as an RWA rating of true (T), true (T), and true (T), buyersand sellers are able to network their needs in advance of traditional“market time”. That is, according to the various embodiments, buyers andsellers are able to network their needs in advance of either partyactually being ready willing and able to sell and as soon as atransaction closes a buyer becomes a future seller with a RWA rating.

FIG. 4 is a time line embodiment associated with property transactionembodiments of the present invention including the ready, willing, andable truth, tables shown in FIGS. 3A and 3B.

As the diagram indicates, traditional “market time” commences with aseller actively marketing property or services when the seller is readywilling and able to sell (e.g., a RWA rating of true (T), true (T), andtrue (T), and ends with a meeting of the minds with a buyer who is readywilling and able to buy (e.g., a RWA rating of TTT).

In contrast to traditional market time, the embodiments described hereinprovide a system and methodology to allow for real property, personalproperty and services to be marketed all the time, before during andafter what would be considered traditional market time. Stated in otherterms, the embodiments described herein are effectively a market, makingmethodology and system.

FIG. 5 illustrates an embodiment for a public interface. As one ofordinary skill in the art will appreciate upon reading this disclosurethe public interface can be provide via a network interface to aproperty transaction server as the same has been illustrated anddescribed in connection with FIGS. 1 and 2.

The methodology and system could be implemented in numerous ways withinvarious markets, although this description will focus on theimplementation of the methodology as exemplified in a real estateprofessional/agent and lender assisted real estate transaction between abuyer and a seller. This embodiment of FIG. 5 illustrates the links toroles that “public” users would assume once they have determined thatthere is value in bartering personal information for membership whetherit is limited or full membership. In the embodiment of FIG. 5, theillustrated roles include; home owners 510, first time home buyers 520,advertisers 530, lenders 540, and agents 550. Embodiments, however, arenot limited to these examples.

As illustrated in the embodiment of FIG. 5 a public user can login intothe system through a “login” module, shown as 560, including definedbusiness rules for login and access as the same will be known andunderstood by one of ordinary skill in the art. In various embodiments,upon logging in to the system, users will signify the role they believethey are by clicking on a hyperlink on a web page. Each of the rolesillustrated above can be implemented as program modules includingcomputer executable instructions in the form of software and/or firmwareto operate on received input data.

As illustrated lathe embodiment of FIG. 5, each of the roles canrespectively provide informational data, shown in block 570, educating aprospective public user as to the benefits of interacting with thesystem. Stated otherwise, the informational data provided in block 570and associated with a particular role will address the WIIFM (What's init for me?) question. As shown in block 580, upon determining that thebenefits of membership outweigh the reasons not to part with personalinformation, the public users can proceed to sign up with the system. Asdescribed in more detail in connection with FIG. 6, upon sign up, publicusers will be identified within the system as members with specificroles.

FIG. 6 is a block diagram representing a login embodiment. As shown inthe embodiment of FIG. 6, the login functionality will direct validatedusers to a user specific “homepage” based on their defined role withinthe system. Thus, as described above, a public interface 602 can beprovided via a network interface to a property transaction server as thesame has been illustrated and described in connection with FIGS. 1 and2. The public interface 602 will lead a user to a login page, as shownin block 604, where the user can enter a username and password. As shownin block 606, program instructions can execute to verify whether aparticular member is validated. One of ordinary skill in the art willappreciate the manner in which program instructions can execute toverify member validation.

As shown in the embodiment of FIG. 6, if a member is validated they canproceed to block 608 where a program application determines the member'srole and displays an appropriate interface. As illustrated in theembodiment of FIG. 6, the program application shown in block 608 canexecute instructions to interact with an account administrator programmodule shown at 610. Collectively, the program application module 608and account administrator module 610 may, upon executing instructionsand operating on available data, determine that the member user is an“account prospect”, e.g., buyer and/or seller, and lead the member userto an account prospect interface as shown at block 612. The programapplication module 608 and account administrator module 610 may, uponexecuting instructions and operating on available data, determine thatthe member user is an “account agent” and lead the member user to anaccount agent interlace as shown at block 614. The program applicationmodule 608 and account administrator module 610 may, upon executinginstructions and operating on available data, determine that the memberuser is an “account advertiser” and lead the member user to an accountadvertiser interface as shown at block 616. Similarly, the programapplication module 608 and account administrator module 610 may, uponexecuting instructions and operating on available data, determine thatthe member user is an “account affiliate” and lead the member user to anaccount affiliate interface as shown at block 618. Each of these exampleinterfaces will be expanded upon in some detail below.

As shown in the embodiment of FIG. 6, if a member is not validated inblock 606 then a public user can choose at 620 to “retry” validatingmembership in block 622. If the “retry” is successful, the member userwill, proceed to the program application module 608 as described above.Additionally, the system can troubleshoot when a public user hasforgotten their password and allow the public user to enter an emailaddress at block 624 and the system can operate on this information toemail a password to a public user as shown at block 626.

Alternatively, if H is determined that a public user is not currently amember user the public user can be offered the opportunity to joinmembership through a public home page as shown at block 628. As shown inthe embodiment of FIG. 6, a public user wishing to join can choose arole as shown at block 630. By way of example and not by way oflimitation, a public user can choose to subscribe as m account prospect632 and be taken to a prospect signup page. In various embodiments, auser subscribing as an account prospect may receive market activityinformation, relating to their particular item of property transactionand other promotional and/or coupon offer access. Additionally, by wayof example and not by way of limitation, a public user can choose tosubscribe as an account agent 634 and be taken to an agent signup page.Further, by way of example and not by way of limitation, a public usercan choose to subscribe as an account advertiser 636 and be taken to anadvertiser signup page. Alternatively, by way of example and not by wayof limitation, a public user can choose to subscribe as an accountaffiliate 634 and be taken to an affiliate signup page. Embodiments arenot limited to these examples.

FIG. 7 is a block diagram representing in more detail an embodiment forthe “my account prospect” block 612 shown in FIG. 6. As mentioned abovein connection with FIG. 6, when buyer and seller member users login tothe system they will be directed to the “my account prospect” page. Asshown in the embodiment of FIG. 7, the “my account prospect” page caninclude a number of links to additional program modules which providevarious additional functionality. In the embodiment of FIG. 7, theadditional functionality is shown as link to a personal profile 710, aseller profile 720, a buyer profile 730, a preference link 740, a browsefunction 750, search function 760, a watch list link 770, a buyer/sellertoolbar 780, and an offer selector link 790. Embodiments, however, arenot limited to these examples. The personal profile 710 will allowbuyers and sellers to provide input data to enter their personal contactinformation. The offer selector link 790 will allow buyers and sellersto express their interests in business from which they would like toreceive special offers. Each of these program modules and theirassociated functionality will be explained farther in the Figures whichfollow.

FIG. 8 is a block diagram representing in more detail an embodiment forthe “seller profile” block 720 shown in FIG. 7. As illustrated in theembodiment of FIG. 8, within the seller profile 720 the seller memberuser will be able to add a new profile, edit their profile, and import aprofile and ultimately set an indicator, e.g., a Ready, Willing and Ableindicator, in association, with a particular piece of property for theseller member user. As one of ordinary skill in the art will appreciateupon reading this disclosure, the system will allow for multipleproperties to be marketed by the same seller within a seller member userprofile.

By way of example and not by way of limitation, a seller profile programmodule can execute instructions through which a seller member user canfirst identify whether a current profile exists, as shown at block 802.If one or more current profiles do exist, then the seller profileprogram module can execute instructions, based on seller member userinput, to allow a seller member user to select a particular profile toview and/or edit, as shown at block 804. As shown in the embodiment ofFIG. 8, as part of editing a given seller profile, a seller member usercan set, update, change, or otherwise modify an indicator levelassociated with that given seller profile as shown in block 806, e.g.,set, modify, or review a RWA status indicator as the same has beendescribed herein.

As illustrated in the embodiment of FIG. 8, if a seller profile does notcurrently exist within a particular seller's profile, the seller profileprogram module can execute instructions through which a seller memberuser can check to see whether a profile exists in a multiple-listingservice (MLS) previous listing or if a profile has been completed byanother network member, as shown at block 808. As shown in theembodiment of FIG. 8, if a profile for a particular item of propertydoes exist, whether in an MLS listing or as completed by another networkmember, the seller profile program module can execute instructions toimport a particular profile into this particular seller member user'sprofile for editing and approval, as shown at block 810.

If, however, a profile for a particular item of property does not exist,e.g., does not exist in an MLS listing or as completed by anothernetwork member, the seller profile program module can executeinstructions to allow a seller member user to create a new sellerprofile relating to a particular item of property, as shown in block812. Further, as shown in the embodiment of FIG. 8, whether a sellermember user imports and edits an existing profile and/or creates a newone the seller profile-program module can execute instructions to allowa seller member user to approve the profile, as shown at block 814. Froman approved seller profile in block 814 the seller member user canproceed to set, update, change, or otherwise modify an indicator levelassociated with that given seller profile as discussed above inconnection with block 806.

FIG. 9 is a block diagram representing in more detail an embodiment forthe “buyer profile” block 730 shown in FIG. 7. As illustrated in theembodiment of FIG. 9, a buyer may create a buyer profile, view the buyerneed(s) the buyer has entered with a previous profile and view, set oralter the buyer ready, willing and able indicator for one of possiblemany buyer profiles for a single buyer.

By way of example and not by way of limitation, a buyer profile programmodule can execute instructions through which a buyer member user canfirst identify whether a current profile exists, as shown at block 902.If one or more current profiles do exist, then the buyer profile programmodule can execute instructions, based on buyer member user input toallow a buyer member user to select a particular profile to view and/oredit, as shown at block 904. As shown in the embodiment of FIG. 9, aspart of editing a given buyer profile, a buyer member user can set,update, change, or otherwise modify an indicator level, associated withthat given buyer profile as shown in block 906, e.g., set, modify, orreview a RWA status indicator as the same has been described herein.

As illustrated in the embodiment of FIG. 9, if a buyer profile does notcurrently exist within a particular buyer's profile, the buyer profileprogram module can execute instructions to allow a buyer member user tocreate a new buyer profile relating to a particular item of property, asshown in block 908. Further, as shown in the embodiment of FIG. 9, oncea buyer member user creates a new profile the buyer profile programmodule can execute instructions to allow a buyer member user to approvethe profile, as shown at block 910. From an approved buyer profile inblock 910 the buyer member user can proceed to set, update, change, orotherwise modify an indicator level associated with that given buyerprofile as discussed above in connection with block 906.

FIG. 10 is a block diagram representing in more detail an embodiment forthe “preferences” block 740 shown in FIG. 7. As shown in the embodimentof FIG. 10, the preferences block 740 can include a relocationnotification link 1010, a buyer notification link 1020, a sellernotification link 1030, an MLS market activity link 1040, an MLSnotification link 1050, a general notifications link 1060, and an oilerselector link 1070. Embodiments, however, are not limited to theseexamples.

According to various embodiments the relocation notification link 1010includes instructions which can be executed by a processor toselectively enable or disable, e.g., turn on or off, a notificationsetting associated with relocations and an item of property. Forexample, an owner of real properly and who is participating in thesystem and/or property transaction device embodiments described hereincan elect to turn on this feature in order to be notified of arelocation buyer's interest in property in the owner's neighborhood. Aswill be described in more detail below, if a relocation buyer likes aparticular neighborhood and would like to see if their buyer need isinteresting to a home owner. According to various embodiments, a buyerparticipating in the system and/or property transaction deviceembodiments could independently access the system to configure or abuyer need description (as the same will be understood upon reading thisdisclosure) and/or an agent participating in the system and/or propertytransaction device embodiments could assist a relocation buyer inputting together a relocation buyer profile, e.g., buyer needdescription, along with possible neighborhoods of interest.

Thus, in one example, a seller's preference setting 1030 can include anindicator representing that a seller would like to receive notificationthat a buyer may be interested in the seller's property. And, a buyer'spreference setting 1020 can include an indicator representing that abuyer would like to receive notification that a seller in a neighborhoodof interest to the buyer may be interested in selling property in thatparticular neighborhood.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, buyer notifications and seller notifications can accommodatea range of sensitivity adjustments. In other words, the buyernotifications and seller notifications, or other items associated withthe preferences block, can execute instructions which allow a user tofilter out notifications based on certain criteria. For example, a buyermay adjust one of the buyer notification settings to a 5 indicatorlevel, e.g. RWA rating, to represent that the buyer only wishes toreceive notifications when a seller is fully ready, willing and a toculminate a transaction relating to a particular item of property. Thiswould result in the buyer only receiving seller notifications fromsellers who have switched their RWA indicator to a “5”.

According to various embodiments, the MLS “My Neighborhood” MarketActivity link 1040 includes instructions which can be executed to allowsellers to adjust the frequency with which they receive email updatesregarding their neighborhood real estate market activity. Similarly, theMLS “Dream Borne” Notification System includes instructions which can.be executed to allow buyers to regulate the frequency and format of theemails the buyer receives regarding matches to the buyer's buyerprofile.

According to various embodiments, the general notifications link 1060includes instructions which are executable to selectably define systemgenerated notifications to be sent to notify a user that an event hasoccurred which may affect a buying or selling decision. In variousembodiments, the offer selector link 1070 includes instructions whichare executable to collect more precise information about a buyer orseller which will increase the likelihood that the advertising displayedon the website and within the buyer and seller emails are appealingenough for the buyer and or seller to read the offer or coupon, print itout and redeem it.

One of ordinary skill in the art will appreciate upon, reading thisdisclosure that various elements associated with, the preferences blockmay be added, deleted and/or modified to suit the needs or as tailoredto a particular market, depending on the types of property or servicesthat are being marketed.

FIG. 11 is a block diagram, representing in more detail an embodimentfor the “browse” block shown in FIG. 7. In the example embodiment ofFIG. 11, the browse diagram refers to real property. Thus, theembodiment of FIG. 11 shows that horn a browse option 1102, a user canchoose between a buyer 1104 and a seller option 1106, and then furtherdefine a state 1108, a region 1110, a map page: and section 1112,property details, including description 1114 photos 1118, a 360 degreetour 1120, etc. The browse diagram is similar to traditional webproperty browsing, except that in accordance with embodiments of thepresent invention, a user (e.g., potential buyer, seller, and/or agent)who is researching her/his competition may pinpoint her/his search downto a map section or neighborhood. One of ordinary skill in the art willappreciate, the manner in which this can be achieved as the same isdiscussed herein in connection with associating map grid data with taxdata for a particular item of property.

As shown in the embodiment of FIG. 11, and as described further herein,the browse block can further includes instructions which are executableto email a friend 1122, express an interest rating 1124, and/or add anitem (e.g., particular piece of property and/or associated party) to awatch list 1126. Further, as shown in the embodiment of FIG. 11, thebrowse block can include instructions which can execute to schedule ameeting between two parties (e.g., a buyer and seller) when a certainlevel of alignment exists between their respective indicators, as thesame is described herein.

FIG. 12 is a block diagram representing in more detail an embodiment forthe “search” block 760 shown in FIG. 7. The search criteria choices willvary based on category of property being sold, for example, realproperly; residential, commercial, farms, lots and land or personalproperty such as farm equipment, ears, boats, etc. In the exampleembodiment of FIG. 12, the search diagram refers to real property. Assuch, the illustrated search criteria includes all available criteriacurrently available via most regional multiple listing services (MLSs).In the various system and property transaction device embodiments,however, none of the properties that are available via this system willbe listed via an MLS. In the various embodiments, all of the propertiesthat are searchable are other users' seller profiles as well as thecapability to perform a buyer profile search from the buyer needsentered into the system.

The embodiment of FIG. 12 shows that from a search option 1202, a usercan choose between a buyer block 1204 which includes instructions thatcan be executed to modify or submit default search criteria and a sellerblock 1206 which includes instructions that can be executed to modify orsubmit default search criteria. As shown in the embodiment of FIG. 12,these search criteria can be submitted to a properties details block,shown at 1208. As one of ordinary skill in the art will appreciate uponreading this disclosure, the properties details block includesinstructions which can be executed to enter numerous property details,including description 1210, photos 1212, a 360 degree tour 1214, etc.The search diagram is similar to traditional web property browsing,except that in accordance with embodiments of the present invention, auser (e.g., potential buyer, seller, and/or agent) who is researchingher/his competition may pinpoint her/his search down to a map section orneighborhood. One of ordinary skill in the art will appreciate themanner in which this can be achieved as the same is discussed herein inconnection with associating map grid data with tax data for a particularitem of property.

As shown in the embodiment of FIG. 12, and as described further herein,the search block can further includes instructions which are executableto email a friend 1216, express an interest rating 1218, and/or add anitem (e.g., particular piece of property and/or associated party) to awatch list 1220. Further, as shown in the embodiment of FIG. 12, thebrowse block can include instructions which can execute to request ashowing between two parties (e.g., a buyer and seller associated with aparticular item of property) when a certain level of alignment existsbetween their respective indicators, as the same is described herein.

FIG. 13 is a block diagram representing in more detail an embodiment forthe “watch-list” block 770 shown in FIG. 7. As one of ordinary skill inthe art will appreciate upon reading this disclosure, the watchlistblock embodiment 1302 of FIG. 13 illustrates a watch list of propertiesor buyers 1302 that a buyer/seller member would like to monitor for anychanges in their respective indicator levels, e.g., ready, willing andable status indicators. As shown in the embodiment of FIG. 13, the watchlist block can include a number of up/down down indicators, e.g.,illustrated as fields 1304, 1310, 1316, reflecting movement in arespective indicator level, e.g., RWA raring status. One of ordinaryskill in the art will appreciate upon reading this disclosure the mannerin which instructions can be executed to operate on, e.g., analyze inputdata, and to output a displayable up/down indicator associated with aparticular entity and/or particular item of property.

In the embodiment of FIG. 13, a “2nd Party RWA (ready, willing, andable) Self Indicator” is shown in a field 1306. As mentioned above asone example, the “2nd Party RWA Self Indicator” can include a ranking ona numerical scale (e.g., in a numerical range of 1-5 with 5 being thehighest value) that the potential buyer or seller has given toherself/himself. In the embodiment of FIG. 13, a “1st Party ranking of2nd Party's property or buyer profile” is shown in a field 1312. By wayof example and not by way of limitation, program embodiments can executeinstructions to allow a buyer or seller to rank properties or buyersagainst each-other, e.g., with a number ranking from 1-100. Embodiments,however, are not limited to these examples and/or a particular numericalrange. In various embodiments, as a buyer or seller ranks another buyeror seller, that buyer or seller will have access to their ranking as ameans to encourage buyers and sellers to fully complete their buyer andseller profiles so they receive a higher ranking and overall higheraggregate ranking.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, by allowing a buyer or seller to rank properties or buyersagainst each-other within a limited number ranking range, e.g., limitedto 100, the system and property transaction device embodiments willencourage the “ranker” to choose which buyers and sellers make it intothe top 100 and which ones don't.

For example, if a seller is in a user's Watch list and changes her/hisRWA status from a 5-2 (e.g., in a numerical range of 1-5 with 5 beingthe highest value), that particular seller may see their aggregaterating drop. As one of ordinary skill in the art will appreciate uponreading this disclosure, program embodiments can execute instructionssuch that once a user ranks another, the ranked user is requested torank the user who just ranked them.

In the embodiment of FIG. 13, another type of “1st party rating of 2ndparty's property or buyer profile” is shown in a field 1318. In variousembodiments this other type of rating can include a standalone ratingwhich may include a “not interested” rating which can serve an indicatorto the system to never show the buyer or seller profile again.

In the embodiment of FIG. 13, a “Picture” field is shown in a field1320, As one of ordinary skill in the art will appreciate this picturefield 1320 can include a thumb nail picture or other a visual reminderof the property in question. Program embodiments can executeinstructions to restrict various pictures according to variousselectable configurations, e.g., the system and property transactiondevice embodiments can be configured such that there are no pictures ofbuyers.

In the embodiment of FIG. 13, a “Map Page and Section” field is shown ina field 1322. In various embodiments, the “Map Page and Section” appliesto the sale of real property only and is an indicator of the map pageand section (e.g., as the same is described herein in association withmap grid data) that the seller's property is located. As one of ordinaryskill in the art will appreciate upon reading this disclosure, there areno map page and section coordinates for buyers.

Further in the example embodiment of FIG. 13, “Price, Bed, Bath andGarage” field are shown as field 1324, 1326, 1328, and 1330. As one ofordinary skill in the art will, appreciate upon reading this disclosure,the “Price, Bed, Bath and Garage” fields are just a sample of possibledata elements on a watch list. Embodiments, however, are not limited tothese examples.

Also shown in the example embodiment of FIG. 13 is a “Setup a Showing”field shown as field 1332. As one of ordinary skill in me art willappreciate upon reading this disclosure, program embodiments can executeinstructions such that if the buyer or seller is less than a 4 (e.g.,continuing to use numerical range example of 1-5 with 5 being thehighest value), this option field will be grayed out and be inactivewith a prompt that the user would have to increase their associatedindicator level, e.g., RWA rating status, in order to request a showing.

FIG. 14 is a block diagram representing in more detail an embodiment forthe “buyer/seller toolbar” block 780 shown in FIG. 7. As one of ordinaryskill, in the art will appreciate upon reading this disclosure, a“toolbar” is an example of an application which may provide immediatenotifications to a user regarding generated device/system events. Theprogram embodiments described herein can be implemented on otherplatforms and networks, e.g., cell phone, voice or text messages, taskbar applications, etc., to attain the same results. As shown in theembodiment of FIG. 14, one example for the “buyer/seller toolbar” blockcan include a link to new email, as shown at 1410, a link to hotproperties, as shown at 1420, a link to hot buyers, as shown at 1430,and a link to hot offers, as shown at 1440. Embodiments, however, arenot limited to these examples. As one of ordinary skill in the art willappreciate upon reading this disclosure, program embodiments associatedwith these links, e.g., 1410, 1420, 1430, and 1440, can be executed asindicators that certain system events have occurred. For example, itsvarious embodiments, the indicators start at 0 and are incremented by 1as a system event is generated that the buyer or seller should be madeaware of.

By way of example and not by way of limitation, the new email link 1410can be for internal email only, e.g., email on a closed system. In thecase of agent assisted real property transactions, all email is receivedand sent to one agent only from a prospect. So for a given buyer orseller me link will only have system generated email in the mailboxalong with email from one particular Realtor. In an unfacilitatedenvironment e.g., outside of the system and property transaction deviceembodiments described herein, buyers and sellers may interact with eachother freely.

Further, by way of example and not by way of limitation, the HotProperties link 1420 can be for properties that are within the sellerprofile criteria of the user and having a specific associated indicatorlevel, e.g., RWA rating. The Hot Buyers link 1430 can be for buyerswhose buyer needs match the user's seller profile description of aproperty. And, the Hot Offers link 1440 can be for oilers, discounts andcoupons that specifically match the settings in offer selector, as thesame has been described above.

FIG. 15 is a block diagram representing in more detail an embodiment forthe “my account agent” block 614 shown in FIG. 6. As shown in theembodiment of FIG. 15, these are examples of options that a real estateagent can see in the case of system network embodiments involving realproperty buyers and sellers. Embodiments, however, are not limited tothis example.

In the example embodiment provided by FIG. 15, an Agent Info Managerlink 1504 is illustrated. Program embodiments associated with the AgentInfo Manager link 1504 can execute instructions to maintain a givenagent user's membership information. Also shown in FIG. 15 is a BillingInformation link 1506. Program embodiments associated with this link1506 can execute in connection with the agent's credit card for billingof monthly membership fee and other marketing fees. The illustratedBrochure Builder link 1508 can be associated with program instructionswhich can execute as an application that allows agents to use templatesto print brochures and have them printed with a local printing partnerfor agent pickup or direct mail. The illustrated Campaign Reports link1512 can be associated with program instructions which can execute togenerate reports for email campaigns which show how many emails weresent out, when, advertisers, percentage of fully advertised, emails, howmany emails opened, how many ads opened, coupons printed, etc.

In the example embodiment provided by FIG. 15, a Relocation Profile link1518 is illustrated. Program embodiments can be executed in associationwith this link 1518 such that stand alone buyer profile input may beprovided by an agent. Program embodiments associated with this link 1518can execute instructions to include map sections or neighborhoods ofinterest. By way of example and not by way of limitation, this link 1518can facilitate the submission of the profile which will triggerrelocation alerts with matching seller profiles if the seller has chosento receive relocation alerts, as the same has been described herein. TheHome Owner Prospector link 1502, the Customer Relationship Managementlink 1510, the Agent Toolbar link 1514, the Homeowner Prospect Capturelink 1516, the My Farm link 1520, and the Map Page Section Auction link1522, can similarly have executable program embodiments associatedtherewith for added particular functionality. Aspects of such addedfunctionality for these embodiments will be describes in the Figures tofollow.

FIG. 16 is a block, diagram representing in more detail an embodimentfor the “home owner prospector” block 1502 shown in FIG. 15. As shown inmore detail here in FIG. 16, the home owner prospector link 1602 canhave executable program embodiments associated therewith to providefunctionality for the creation of a network, of buyers and sellers ofreal property. As shown in the example embodiment of FIG. 16, programinstructions can execute in association with using a multiple listingservice (MLS) 1604, or individual counties. The program embodimentsexecute instructions to import all tax payer data into a database of thenetwork system embodiments described herein. As shown in FIG. 16,program embodiments can further execute instructions in association withother map databases 1608, such as other servers or third party contentproviders as the same has been described in connection with FIGS. 1 and2.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, the program embodiments can execute instructions to identifythe official map book of the local MLS. In various embodiments, the mapbook company can upload all map data to a server accessible by thenetwork system embodiments. Likewise, in various embodiments, a map bookcompany, e.g., TPC, can upload identifying micromotion for each parcelidentifier (PID) to a server accessible by the network systemembodiments holding the map data. Program embodiments can executeinstructions in conjunction with the map company to associateappropriate coordinates, e.g., geographic coordinates of latitude andlongitude, to identify which map section a property is in.

One of ordinary skill in the art will appreciate upon reading thisdisclosure various manners in which this can be achieved. For example, aPID, street address or latitude and longitude (lat/lon) can be sent inbulk or individually via a web service to the map data store. Programinstructions can execute to perform a lookup on the given informationand share these with the map company which can then determine the mappage and section within which the PID lies. As shown in the embodimentof FIG. 16, the PID can be returned to the network system embodimentswith the associated map page and section information. As one of ordinaryskill in the art will appreciate, the end result is that any particularaddress can he associated with a map page and section.

As in the example of FIG. 16, program instructions can execute such thatafter an agent authenticates as a member and chooses “Home OwnerProspector” a page, e.g., client interface page 1610, will appear whichwill prompt the agent to input a map page and section. In variousembodiments, upon submission, the application will return a list ofsubdivisions, as shown in block 1620, within that map page and sectionwith a sub-list of street names below each subdivision. The agent canclick on the subdivision that the agent would like to canvas or senddirect mail to and the names of the homeowners, their addresses and aspace for their email address will follow, as shown in block 1622.

As illustrated in block 1624 of this embodiment, the agent may choose tosave the list. In various embodiments, upon saving the list programinstructions can execute to place a soft hold, e.g., register a softlock for a period of time, on the list which notifies any other agentswho save the same list that the list has been saved within this periodof time, e.g., past week, by another agent. Further, the agent maychoose one or more prospecting methods, e.g., door to door or directmail campaign as shown in block 1626. As shown in FIG. 16, the list maybe printed, as shown at block 1628, and/or submitted for a direct mailcampaign to a printing and mailing service, as shown in 1630 and 1632.

FIG. 17 is a block diagram representing in more detail an embodiment forthe “customer relationship management” block 1510 shown in FIG. 15. Asshown in more detail here in FIG. 17, the customer relationshipmanagement link 1510 can have executable program embodiments associatedtherewith to provide functionality and features used to track theevolution of the relationship between the customer and the agent overtime.

In the example embodiment of FIG. 17 a Customer Lookup link 1710 isillustrated. Program embodiments can be executed in association withthis link 1710 to allow multiple methods for an agent to lookup acustomer's information, for example, by name, address, map section,email address, etc. As one of ordinary skill in the art will appreciateupon, reading this disclosure, all agents can have direct access totheir customer's buyer profiles, e.g., shown as link 1720, sellerprofiles, e.g., shown as link 1730, and all of the statistics associatedwith each, e.g., number of matches by rating, rank, etc, shown as 1725and 1735 respectively. Embodiments are not limited to these examples.

In the example embodiment of FIG. 17 a Customer History link 1740 isillustrated. In various embodiments, program instructions can beexecuted in association with this link 1740 to provide a completehistory of communication with a particular prospect as well as an emailtrail. Further, in the example embodiment of FIG. 17, a Customer Hotlist1750 is illustrated. And, in various embodiments, program instructionscan be executed in association with this link 1750 to provide agentswith access to ail buyer and seller hot lists, as the same have beendescribed herein.

FIG. 18 is a block diagram representing in more detail an embodiment forthe “customer hotlist” block 1750 shown in FIG. 17. As shown in moredetail here in FIG. 18, the customer hotlist link 1510 can haveexecutable program embodiments associated therewith to providefunctionality and features usable from within the agent's customerrelationship management system. In the example embodiment of FIG. 18,the fields on the left can be provided as and represent columns of data,in the example embodiment of FIG. 18, the example fields arebuyer/seller indicator 1802, up/down indicator 1804, new status 1806,previous status 1810, seller name 1812, address 1814, subdivision 1816,etc. Fields 1820-1, . . . , 1820-N represent that any number of fieldsmay be chosen. Embodiments are not limited to these examples.

One of ordinary skill in the art will appreciate upon reading thisdisclosure that the agent's customers can be provided as and listed inrows. As shown in the embodiment at block 1830, program instructions canexecute such that when the agent clicks on her/his customer's name thecustomer's information pops up listing their new RWA status, e.g., zoomin prospect status.

FIG. 19 is a block diagram representing in more detail an embodiment forthe “zoom in prospect status” block 1830 shown in FIG. 18. As shown inmore detail here in FIG. 19, the zoom in prospect status link can haveexecutable program embodiments associated therewith to providefunctionality and features such that for each customer an agent would beable to preview a number of top ranking buyer matches on the customerswatch list (e.g., fop 5 matches) and a number of top ranking new/unratedbuyers (e.g., top 5 new/unrated buyers), e.g., top ranking buyer andseller statuses associated with a particular item of property asillustrated in fields 1902 and 1904 respectively.

Further, as shown in the embodiment of FIG. 19, the agent would be ableto email either the buyers interested in the customer's property, e.g.,as illustrated with link 1906, or the sellers whose property thecustomer is interested in, e.g., as illustrated by link 1908, or both.As one of ordinary skill in the art will appreciate upon reading thisdisclosure, this enablement in the network system and propertytransaction device embodiments described herein is designed as a way forthe customer to click on the report and interact with their watch list.

FIG. 20 is a block diagram representing in more detail an embodiment forthe “agent toolbar” block 1514 shown in FIG. 15. As shown in theembodiment of FIG. 20, one example for the “agent toolbar” block caninclude a buyer match link as shown at 2010, a seller match link asshown at 2020, an email link as shown at 2030, a relocation alert linkas shown, at 2040, a buyer level indicator (e.g., buyer RWA status) linkas shown at 2050, a seller level indicator (e.g., seller RWA status)link as shown at 2060, a new prospects link as shown at 2070, and a newcustomers link as shown at 2080. Embodiments, however, are not limitedto these examples. As one of ordinary skill in the art will appreciateupon reading this disclosure, program embodiments associated with, theselinks, e.g., 2010, 2020, 2030, 2040, 2050, 2060, 2070, and 2080, can beexecuted as indicators that certain system events have occurred.

By way of example and not by way of limitation, the embodiment of FIG.20 depicts the text links within and agent specific-internet Explorertoolbar as the same will be known and understood by one of ordinaryskill in the art. In various embodiments, an agent will be notifiedwhen, a customer is at a particular indicator level status, (e.g., a 5,in a numerical range of 1-5 with 5 being the highest value) and a buyeror seller matches that customers buyer or seller need (e.g., also has anindicator level status of a 5).

In the example embodiment provided by FIG. 20, program embodimentsassociated with the email link 2030 can execute instructions to providea notification that a new system or customer correspondence is in theagent's internal web based email box. Program embodiments associatedwith the relocation alert link 2040 can execute instructions to indicatethat there is a relocation buyer who is interested in a particularneighborhood.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, program, instructions executing in connection with thisfeature provides a heads up that a customer who owns a house in thatneighborhood may be calling or sending an email that they are interestedin setting up a one time showing for the relocation customer. Further asprogram instructions execute in connection with tins feature, when aseparate agent submits that they have a relocation buyer or perhaps afirst time home buyer the emails that go out to the homeowners in theneighborhood of interest will actually have a reply to an email addressof the agent that originally signed them up or that they havesubsequently chosen.

Program embodiments associated with the buyer RWA status link 2050 canexecute instructions to notify an agent of a customer's upgrade of anRWA status according to the notification rules, e.g., as describedherein, in association with notice preferences. Likewise, programembodiments associated with the seller RWA status link 2060 can executeinstructions to notify an agent of a customer's upgrade of an RWA statusaccording to the notification rules.

In various embodiments, program instructions can execute in connectionwith the new prospects link 2070 to provide notifications of a housethat has sold within a section within which the agent has prospects orif the agent has paid for the section, within the agent's exclusivesection. Additionally, program instructions can execute in connectionwith the new customers link 2080 to identify customers who have justsigned up or transferred from another agent to the logged in agent.

FIG. 21 is a block diagram representing in more detail an embodiment forthe “home owner prospect capture” block 1516 shown in FIG. 15. As shownin the embodiment of FIG. 21, the “home owner prospect capture” blockincludes programs instructions which can execute in association with anumber of displayable pages and/or links to allow an agent to performadditional home owner prospecting. For example, the agent would go tothe home owner prospect capture pages after the agent is finished withcollecting email addresses in order to capture the email addresseswithin the system.

In the example embodiment provided by FIG. 21, a list select link isillustrated at 2110. As one of ordinary skill, in the art willappreciate upon reading this disclosure, an agent can execute programinstructions in connection with this link to select a list from savedprospect lists. In the example embodiment provided by FIG. 21, programinstructions can execute in connection with an edit link 2120 to entercaptured addresses or update owner information with an email address.Thus, for example, at this point the agent, may recall a savedprospecting list in order to enter captured addresses or update ownerinformation with an email address.

Further, in the example embodiment provided by FIG. 21, an associationlink is illustrated at 2130. As one of ordinary skill in the art willappreciate upon reading this disclosure, an agent can execute programinstructions in connection with this link such that a customer isassociated with and individual agent to receive and deliver network,based communications regarding hosting showings or setting up buyershowings for properties in which the customer is interested.Embodiments, however, are not limited to these examples.

FIG. 22 is a block diagram representing in more detail an embodiment forthe “map page section auction” block 1522 shown in FIG. 15. According tovarious embodiments of the network system and property transactiondevice, agents will have an opportunity to bid on exclusive listingsand/or representations in association with particular items of property.

In the case of real property, agents have the opportunity to bid onexclusive rights for all map sections for a particular region. Forexample, if an agent would like to increase their market share in aparticular section, or maintain their market share an agent can executeprogram instructions to place a map section bid using a link asillustrated at 2210. As further illustrated in this example, an agentcan execute program instructions to cheek map section bid status using alink as illustrated at 2220.

One of ordinary skill in the art will appreciate upon reading thisdisclosure the manner in which such an auction can be implemented andconducted in the network system and property transaction deviceembodiments described herein. By way one example and not by way oflimitation, upon placing the bid in an auction and successfully winningthe agent in the case of real property would have exclusive rights tosecure the email addresses of the property owners in that section for aspecified period of time. In various embodiments, the auction processmay take place in any form, e.g., silent auction, sealed bids, ascendingor descending.

Embodiments as described herein enable items of property, e.g., a regionof real property, to be divided up by sections of map grid data andenable assigning and recording exclusive rights to particular agents tomarket to the property owners. In various embodiments, a stipulation mayalso be made within the system such that if an agent with exclusiverights to secure a property owner's email address within the system hassecured the address, and, following the successful capture of the emailaddress, the property owner decides to choose another member agentwithin the system or invite an agent to join, then the agent whocaptured the email address may he entitled to a commission. Embodiments,however, are not limited to these examples.

FIG. 23 is a block diagram representing in more detail an embodiment forthe “my farm” block 1520 shown in FIG. 15 illustrating detail for mapsection value and market share. As shown in the embodiment of FIG. 23,one example for the “my farm” block can include a map link as shown at2302, a top agent link as shown at 2304, a filter module as shown at2306, an agent report module as shown at 2308, and a commission moduleas shown at 2310. There can further be included program embodimentswhich execute instructions to provide access to performance based linksas illustrated at 2350. Embodiments, however, are not limited to theseexamples. As one of ordinary skill in the art will appreciate uponreading this disclosure, program embodiments associated with those linksand/or modules, e.g., 2302, 2304, 2306, 2308, 2310, 2312, and 2350, canbe executed as indicators that certain system events have occurred.

As one example, the embodiment of FIG. 23 is discussed in connection,with real property. Embodiments, however, are not limited to thisexample. In the case of real property transactions the map link 2302 caninclude a regional map of real property data, e.g., the regional map caninclude an “official” map used by any regional multiple listing service(MLS). For example, in the Twin Cities (Minneapolis/St. Paul, Minn.)market, the locally known “King's Map” could be provide via programinstructions executing in connection with the map link 2302. To use thisexample at tits time of this disclosure, the map link 2302 would theninclude 229 pages, 20 sections pages, and 4580 pages, for instance.

The follow tills example, the top agent link as shown at 2304 caninclude executable instructions associated with program embodiments todisplay the top three listing agents sorted by map page and section, byvolume, and then total sales dollars. Embodiments, however, are limitedto these examples. One of ordinary skill in the art will appreciate uponreading this disclosure the manner in which program embodimentsdescribed herein can execute instructions to extract any selectablenumber of top listing agents and to sort the same according to variousselectable categories. In various embodiments, either in a printablefashion or via a computer application, program instructions can executeto extract the top listing agents who closed sales, e.g., the top 3agents, within any section within the past year by volume or transactiondollars, etc.

In various embodiments, a filter module as illustrated at 2306 isprovided. One of ordinary skill in the art will appreciate upon readingthis disclosure the manner in which program instructions can execute aspart of a filter module to filter out all agents not meeting aselectable criteria. To follow in the above example, all agents notwithin the top number, e.g., 3 for this example, will be filtered out.

In various embodiments, a report module as illustrated at 2308 isprovided. One of ordinary skill in the art will appreciate upon readingthis disclosure the manner in which program instructions can execute aspart of a report module to report agents within the selectable topnumber. To follow in the above example, top producing agents per sectionmay be available by print or via a computer application.

In various embodiments, a commission module as illustrated at 2310 isprovided. One of ordinary skill in the art will appreciate upon, readingthis disclosure the manner in which, program instructions can execute aspart of a commission module to provide displayable commission data basedon a number of selectable criteria. For example, program instructionscan executes as part of a commission module to section wide list sidecommissions, e.g., based on a three percent (3%) commission.

In various embodiments, a value module as illustrated at 2310 isprovided. One of ordinary skill in the art will appreciate upon readingthis disclosure the manner in which program instructions can execute aspart of a value module to provide displayable value data based on anumber of selectable criteria. For example, program instructions canexecute as pars of a commission module to provide base value of asection determined as a percentage of the average list side commission.

Again, one of ordinary skill in the art will appreciate upon readingthis disclosure that the embodiments are not limited to real propertyapplications and/or to the examples given herein. One of ordinary skillin the art will further appreciate upon reading this disclosure that theperformance based links illustrated at 2350 can provide additionallevels of access and user rights to users, e.g., agents falling withinselectably defined classes. For example, qualifying agents will have theability to view their most productive sections by volume and transactiondollars as illustrated at 2352. In various embodiments, based on thedata available to the agent, the agent will have the opportunity toplace a bid via an auction for the exclusive right to market to aspecific region as illustrated at 2354. In various embodiments, therights can be selectably configured, by the execution of programinstructions to only extend to recording property owners email addresseswithin this system.

FIG. 24 is another block diagram, representing in more detail anembodiment for the “my farm” block 1520 shown in FIG. 15 illustratingdetail for market share analysis per map page section. As one ofordinary skill in the art will appreciate upon reading this disclosure,the my farm block embodiment of FIG. 24 can include program instructionsthat execute in association with a farm reports link 2402 and/or apre-selling link 2404, as just one example. Together with these examplelinks, program instructions can execute to selectively display a numberof fields, illustrated in the example embodiment of FIG. 24 as 2406,2408, 2410, 2412, 2414, 2416, 2418, 2420, 2422, 2424, and 2426. Theexample embodiment illustrated in connection with FIG. 24 demonstratesthat program embodiment can executes instructions in association withvarious features and functionality to provide displayable reports.

For example, the displayable report embodiment of FIG. 24 illustrates areport that can enable agents to view the value of a section to aparticular agent by total volume or transaction dollars for a map pageand section, e.g., fields 2406 and 2408. Also illustrated are fieldsshowing total closed listings as 2410, and average sales price 2412. Inthe embodiment of FIG. 24, program embodiments can execute instructionsto rank section dollars or closed transactions to match a user'sanalysis choice as shown in field 2416. As shown in the embodiment ofFIG. 24, fields can additionally be provided illustrating total listings2418 and average sales price 2420. As illustrated in field 2422, thelist side commission estimate is displayable and, by execution ofprogram instructions is adjustable and can be different by region.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, within the same row, an agent may view how they compare tototal listings per section in the last year as well as average saleprice, average estimated list side commission. In the embodiment of FIG.24, a field 2424 is illustrated, by execution of program instructions,to allow the individual agent to compare their market share in a givensection to the rest of the market. Further, as illustrated by theembodiment of FIG. 24, program embodiments can execute instructions toallow agents to reserve a section associated with map data and/or bid ona section via an auction, as illustrated in field 2426 and as the samehas been described herein. Embodiments, however, are not limited to theexamples provided in FIG. 24. Thus, as stated in a previous Figuresdiscussion, program embodiments can execute instructions to divide upinto sections, assign (sell), and track information on regionsassociated with map data and particular member agents.

FIG. 25 is a block diagram representing an embodiment for establishingan indicator level associated with a seller of property. For example,from a seller profile link, as the same has been described herein,program embodiments can be executed based on user input to establish anindicator level associated with a seller and/or seller's property. Inthe embodiment of FIG. 25, a seller indicator level is represented asnumerical indicator (e.g., in a numerical range from 1 to 5 with 5 beingthe most proactive) and expressed here as ready, willing, and able (RWA)indicator. As described above, the ready, willing, and able factors areassociated with an individual's state of mind as influenced by variouslife circumstances as the same have been described above. As describedherein, a given RWA numerical indicator level ratings can be subjectiveto the user, but according to the execution of program instructions canbe determined in association, with definable general rating guidelinesand definable business rules described in the network system embodimentsand property transaction device embodiments discussed.

Thus, by way of example and not by way of limitation, the embodiment ofFIG. 25 illustrates a flow chart documenting a property owner'stransition from an indicator level expression in the numerical range of1-3 to a 4 or 5. As has been described herein, a change from, oneindicator level expression to another may be controlled by programinstruction execution according to defined business rules. Toillustrate, in block 2502 a seller may change, e.g., adjust up and/ordown, their numerical indicator level within a numerical range from 1-3in an unrestricted manner.

At block 2504, a seller user attempts, e.g., requests based on input, tochange their numerical indicator level to a 4 or 5. In this exampleembodiment, e.g., associated with real property, at block 2506 programinstructions will execute, based on user input, to verify user identity.For example, the program embodiments can execute to request a creditcard number or other financial account number to verify and authenticatethe user's identity. As one of ordinary skill in the art will appreciateupon reading this disclosure, such verification can be used to confirmthe item of property associated with the seller is the seller'sprinciple residence, etc. In other words, once a property owner changestheir rating from a 1-3 to a 4 or 5, program instructions can execute toverity the item of property, verified as owned by a particular user, isthe property owner's principle residence. One of ordinary skill in theart will further appreciate upon reading this disclosure that theprogram embodiments can execute instructions to verify such informationby performing a match up of a particular property address with thebilling address of the credit card provided by the user.

Further, as illustrated in block 2508, program embodiments can executeinstructions such that an agent may be notified via the agent's toolbar,as the same has been described herein, of the status change. In variousembodiments, program instructions are executed such that when a sellerhaving an RWA indicator from 1-4 (e.g., block 2510) changes their readywilling and able rating of a 1-4 to a 5 (e.g., block 2512), and forexample signs a showing agreement, the agent and seller can coordinate ashowing schedule and/or a one time showing contract as shown in block2514. As shown in blocks 2516 and 2518, program embodiments can furtherexecute such that buyers, and/or agent sponsors, will be notified whohave expressed interest in the property and have a buyer RWA rating ofat least a 3-5.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, such a set of restrictions is one example of the definablebusiness rules which can be implemented by execution of the programembodiments described herein. Embodiments, however, are not limited tothese examples.

FIG. 26 is a block diagram representing an embodiment for establishingan indicator level associated with a buyer of property. For example,from a buyer profile link, as the same has been described herein,program, embodiments can be executed based on user input to establish asindicator level associated with a buyer's interest in a particular itemof property. In the embodiment of FIG. 26, a buyer indicator level isagain represented as numerical indicator (e.g., in a numerical rangefrom 1 to 5 with 5 being the most proactive) and expressed here asready, willing, and able (RWA) indicator. As described above, the ready,willing, and able factors are associated with an individual's state ofmind as influenced by various life circumstances as the same have beendescribed above. And, as described above, a given RWA numericalindicator level ratings can be subjective to the user, but according tothe execution of program instructions can be determined in associationwith definable general, rating, guidelines and definable business rulesdescribed in the network system, embodiments and property transactiondevice embodiments discussed.

Thus, by way of example and not by way of limitation, the embodiment ofFIG. 26 illustrates a flow chart-documenting a buyer's transition froman indicator level expression in the numerical range of 1-4 to a 5. Ashas been described herein, a change from one indicator level expressionto another may be controlled by program instruction execution accordingto defined business rules. To illustrate, in block 2602 a buyer maychange, e.g., adjust up and/or down, their numerical indicator levelwithin a numerical, range from 1-4 in an unrestricted manner.

At block 2604, a buyer user attempts, e.g., requests based on input, tochange their numerical indicator level to a 5. In this exampleembodiment, e.g., associated with real property, at block 2606 programinstructions will execute, based on user input, to verify user identity.For example, the program embodiments can execute to request a creditcard number or other financial account number to verify and authenticatethe user's identity. Additionally, however, as shown in the embodimentof FIG. 26, the program embodiments can execute instructions to promptthe user to choose a lender, e.g., to select a lender associated withthe system network embodiments and property transaction deviceembodiments described herein, in order to be pre-approved tor a specificloan amount.

As illustrated in the embodiment of FIG. 26, the pre-approval may berecorded as valid for a particular time period, e.g., 6 months, and theverification may be conducted and recorded as a one time process. Thus,when a buyer changes her or his RWA rating from any number to a 5 thebuyer will be prompted to choose a lender within the network in order tobe pre-approved for a specific loan amount. In various embodiments, oncea network member lender has indicated pre-approval and the amount of thepre-approval, program instructions can execute such that the buyer's RWArating will automatically be come a 5 adjustable down by the buyer atany time and back to a 5 within a period of time to be preadjusted by anadministrator. In this manner, the buyer will be preapproved to buyproperty up to a certain dollar amount.

Further, as illustrated in block 2608, program, embodiments can executeinstructions such that an agent may be notified via the agent's toolbar,as the same has been described herein, of the status change. In variousembodiments, program instructions are executed such that when a buyerhaving an RWA indicator from 1-4 (e.g., block 2602) changes their readywilling and able rating to a 5 matching sellers having an RWA of atleast 4-5 will be notified.

As one of ordinary skill in the art will appreciate upon reading thisdisclosure, such a set of restrictions is one example of the definablebusiness rules which can be implemented by execution of the programembodiments described herein. Program embodiments can executeinstructions in association with the above example to coordinate ashowing once the defined business rules have been satisfied. The readerwill appreciate that embodiments are not limited to these examples.

FIGS. 27 and 28 illustrate various method embodiments for propertytransactions. As one of ordinary skill in the art will understand, theembodiments can he performed by software/firmware (e.g., computerexecutable instructions) operable on the devices shown herein orotherwise. The embodiments of the invention, however, are not limited toany particular operating environment or to software written in aparticular programming language. Software, application modules, and/orcomputer executable instructions, suitable for carrying out embodimentsof the present invention, can be resident in one or more devices orlocations or in several locations.

Unless explicitly stated, the method embodiments described herein arenot constrained to a particular order or sequence. Additionally, some ofthe described method embodiments or elements thereof can occur or beperformed at the same point in time.

FIG. 27 illustrates one method embodiment for a property transaction. Asshown in the embodiment of FIG. 27 the method includes providing anelectronic bidirectional communication conduit over time that connectsunassociated owners and purchasers to one another in advance of an owneroffering an item of property for sale, at block 2710. Providing anelectronic bidirectional communication conduit over time that connectsunassociated owners and purchasers includes any of the devices, networksystems, and techniques, as the same have been described above.

At block 2720, the method includes electronically recording an indicatorlevel for a party interested in the item of property. Electronicallyrecording an indicator level for a party interested in the item ofproperty includes any of the devices, network systems, and techniques,as the same have been described above. At block 2730, the methodincludes communicating the recorded indicator to one or more parties toculminate a transaction for the item of property. Communicating therecorded indicator to one or more parties to culminate a transactionincludes various techniques, devices, and systems as the same have beendescribed herein.

FIG. 28 illustrates another method embodiment for a propertytransaction. As shown in the embodiment of FIG. 28 the method includesidentifying a section on a map grid having a number of items suitablefor a transaction, at block 2810. Identifying a section on a map gridincludes the methods and techniques described above and herein.

At block 2820, the method includes assigning the section to a particularentity. Assigning the section to a particular entity includes using anyof the devices, network systems, and techniques, as the same have beendescribed above. At block 2830, the method includes associating at leastone indicator with each item on the map grid. As one of ordinary skillin the art will appreciate upon reading this disclosure, associating atleast one indicator with each item on the map grid includes using any ofthe devices, network systems, and techniques, as the same have beendescribed above.

Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the art will appreciate that anarrangement calculated to achieve the same techniques can be substitutedfor the specific embodiments shown. This disclosure is intended to coveradaptations or variations of various embodiments of the invention.

It is to be understood that the above description has been made in anillustrative fashion, and not a restrictive one. Combination of theabove embodiments, and other embodiments not specifically describedherein will be apparent to those of skill in the art upon reviewing theabove description. The scope of the various embodiments of the inventionincludes other applications in which the above structures and methodsare used. Therefore, the scope of various embodiments of the inventionshould be determined with reference to the appended claims, along withthe full range of equivalents to which such claims are entitled.

In the foregoing Detailed Description, various features are groupedtogether in a single embodiment for the purpose of streamlining thedisclosure. This method of disclosure is not to be interpreted asreflecting an intention that the embodiments of the invention requiremore features than arc expressly recited in each claim.

Rather, as the following claims reflect, inventive subject matter liesin less than all features of a single disclosed embodiment. Thus, thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separate embodiment.

1-20. (canceled)
 21. A computerized system for determining a likelihoodof a seller of real property entering into a transaction for the realproperty, comprising: a computer; a database of prospective sellers;software adapted to execute on the computer that positions and displaysprospective seller information on a map; means for populating thedatabase with a set of characteristics for each prospective seller;software adapted to execute on the computer that utilizes the databasewith the set of characteristics to produce at least one indicator valuethat indicates a likelihood of each prospective seller entering into atransaction with a buyer; and means for presenting information to a userbased on the values that indicate the likelihood of prospective sellersentering into a transaction for the real property.
 22. The system ofclaim 21 where the sellers are providers of services.
 23. The system ofclaim 21 where information for the set of characteristics for a givenprospective seller is entered into the database by the given prospectiveseller.
 24. The system of claim 21 where information for the set ofcharacteristics for each prospective seller is automatically collectedby and entered into the database by the means for populating thedatabase.
 25. The system of claim 21 where the means for presentingdisplays the value for the likelihood of at least one prospective sellerentering into a transaction on a map.
 26. The system of claim 21 whereone of the set of characteristics indicates a seller's self-reportedwillingness to sell.
 27. A computerized system for determining alikelihood of a buyer entering into a transaction for real property,comprising: a computer; a database of prospective buyers; softwareadapted to execute on the computer that positions and displaysprospective seller information on a map; means for populating thedatabase with a set of characteristics for each prospective buyer;software adapted to execute on the computer that utilizes the databasewith the set of characteristics to produce at least one indicator valuethat indicates a likelihood of each potential buyer entering into atransaction with a seller of the real property; and means for presentinginformation to a user based on the values that indicate the likelihoodof potential buyer's entering into a transaction for the real property.28. The system of claim 27 where the buyers are buyers of services. 29.The system of claim 27 where information for the set of characteristicsfor a given potential buyer is entered into the database by the givenpotential buyer.
 30. The system of claim 27 where the means forpresenting displays the value for the likelihood of at least onepotential buyer entering into a transaction on a map.
 31. The system ofclaim 27 where one of the set of characteristics indicates the buyer'sself-reported ability to buy.